<?xml version='1.0' encoding='utf-8' ?><!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html xmlns="http://www.w3.org/1999/xhtml">
	<head>
		<meta http-equiv="Content-Type" content="text/html; charset=utf-8"/>
		<title>60. Operational Analysis</title>
		<link type="text/css" rel="stylesheet" href="PLUGINS_ROOT/org.polarsys.capella.doc/html/styles.css"/>
	</head>
	<body>
		<h1 id="OPERATIONAL_ANALYSIS">OPERATIONAL ANALYSIS</h1>
		<h3 id="DEFINITION">DEFINITION</h3>
		<p>Before and beyond System/Software requirements, Operational Analysis focuses on the customer needs and goals. Its objective is to ensure good adequacy of System/Software definition with regards to its real operational use.</p>
		<p>Outputs of Operational Analysis consist mainly in an &lsquo;operational architecture&rsquo; describing and structuring this need in terms of Actors/Users, their Operational Capabilities and Activities, operational use Scenarios giving dimensioning parameters, operational constraints including safety, security, system life cycle&hellip;.</p>
		<h3 id="ICONS">ICONS</h3>
		<p>
			<img height="66" width="75" border="0" src="Images/60.%20Operational%20Analysis_html_m5da03533.png"/>
		</p>
	</body>
</html>